Repository navigation
fix: cap mcp below 2 so uipath-dev-mcp starts on a fresh install - #144
vishalhabib99 wants to merge 4 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Hi, just checking whether this one is on your radar. It's a small fix ( |
|
hi @vishalhabib99 |
radu-mocanu
left a comment
radu-mocanu
left a comment
There was a problem hiding this comment.
please also bump the patch version of uipath-mcp so the changes are published to pypi
|
Thanks @radu-mocanu! Bumped the patch version to 0.0.88 (pyproject.toml + the uv.lock entry), since 0.0.87 is already on PyPI. If you meant a different package by |
Problem
uipath-dev0.0.86 on PyPI requiresmcp[cli]>=1.0.0with no upper bound, so a freshuv add uipath-devorpip install uipath-devresolves mcp 2.3.0.src/uipath/dev/mcp/__init__.pyimportsfrom mcp.server.fastmcp import Context, FastMCP, and mcp 2.x removed that module, souipath-dev-mcpfails on startup:The repo's own
uv.lockpins mcp 1.26.0, so development checkouts are fine. Only installs from PyPI are affected.Change
mcp[cli]>=1.0.0,<2inpyproject.toml, with the matching specifier inuv.lock. The locked version (1.26.0) is unchanged. Moving to the mcp 2.x API (MCPServer) can be a separate change.Checked
uv pip compile(Python 3.12)from mcp.server.fastmcp import Context, FastMCPuipath-devas publishedmcp==2.3.0ModuleNotFoundErrormcp[cli]>=1.0.0,<2mcp==1.30.0The fix reaches users with the next release.